Shared-disk architecture
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
top
A shared-disk architecture (SD) is a distributed computing architecture in which the nodes share same disk devices but each node has its own private memory.cite-ref-1[1] The disks have active nodes which all share memory in case of any failures.cite-ref-2[2] In this architecture, the disks are accessible from all the cluster nodes. This architecture has quick adaptability to the changing workloads.cite-ref-3[3] It uses robust optimization techniques. Multiple processors can access all disks directly via intercommunication network and every processor has local memory.
It contrasts with shared-nothing architecture, in which all nodes have sole access to distinct disks,cite-ref-stopford-4-0[4] and with shared-memory, in which they also share memory.
Shared-disk has two advantages over Shared-memory. Firstly, each processor has its own memory, the memory bus is not a bottleneck; secondly, the system offers a simple way to provide a degree of fault tolerance.
References
cite-note-11. ↑ "Difference between Shared Nothing Architecture and Shared Disk Architecture". GeeksforGeeks. 2020-05-18. Retrieved 2021-02-24.
cite-note-22. ↑ "Solar: Towards a Shared-Everything Database on Distributed Log-Structured Storage" (PDF): 13 – via Solar. {{cite journal}}: Cite journal requires |journal= (help)
cite-note-33. ↑ citerefrylan2018Rylan, John (1 April 2018). "Big Database (Part 2): Database Architecture". DZone.
cite-note-stopford-44. ↑ "Shared Nothing v.s. Shared Disk Architectures: An Independent View". November 24, 2009. Retrieved November 1, 2012.